home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Amiga Collections: Camelot
/
Camelot 070 (1990-04)(Swedish User Group of Amiga)(SE)(PD)[WB].zip
/
Camelot 070 (1990-04)(Swedish User Group of Amiga)(SE)(PD)[WB].adf
/
ParNet
/
ppn-net.doc
< prev
next >
Wrap
Text File
|
1990-01-07
|
8KB
|
275 lines
/* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *\
* |_o_o|\\ Copyright (c) 1989 The Software Distillery. *
* |. o.| || All Rights Reserved *
* | . | || Written by John Toebes and Doug Walker *
* | o | || The Software Distillery *
* | . |// 235 Trillingham Lane *
* ====== Cary, NC 27513 *
* BBS:(919)-471-6436 *
\* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * */
This material is Copyright (C) 1988 and 1989 The Software Distillery.
The Parallel Port Network code (PPN code) is Copyright (C) 1989 by Matthew Dillon.
This project brought to you by:
John Toebes and Doug Walker (NET: handler, lots and lots of code)
Matthew Dillon (PPN code communications module)
It may be distributed freely as long as the following restrictions are met:
1. All files present in the distribution package must be redistributed
with the package, including this documentation file. If you
distribute on diskette, all files must be on a single diskette.
2. The distributor may charge a fee to recover distribution costs.
The fee for diskette distribution should not be more than the cost
to obtain the same diskette from Fred Fish or The Software Distillery,
whichever is greater. Current charge from The Software Distillery
is $6 per disk, including all postage and handling charges.
3. The distributor agrees to cease distributing the programs and data
involved if requested to do so by authors or any member of The
Software Distillery.
------------------------------DISCLAIMER
Neither The Software Distillery nor any of its members will be liable for
any damage arising from the failure of this program to perform as described,
or any destruction of other programs or data residing on a system
attempting to run the program. While we know of no damaging errors, the
user of this program uses it at his or her own risk.
-----------------------------FUNCTIONALITY
RUNNING THE NETWORK HANDLER:
Machine A has your HDs, Machine B wants to access Machine A's HDs.
1. You need to make a custom DB25 cable, refer to CABLE.DOC for
instructions on how to make the cable.
2. Connect the cable between Machine A and B's parallel port.
- Double check the wiring of the cable as per CABLE.DOC before
connecting it.
- Always connect the cable with both machines off.
3. Copy NETPAR-HANDLER to L: on Machine B's boot floppy.
4. Append the included Mountlist entry to DEVS:Mountlist on Machine B's
boot floppy.
5. Copy NETPAR-SERVER to C: on Machine A (it can actually go anywhere).
6. Issue the CLI command "ASSIGN ROOT: <path>" on machine A. This
determines where machine B will have initial access to.
7. Copy NODE.INFO ROOT: (on machine A)
This file contains the .info information for the remote node that will
be displayed on the workbench screen of the local node. Feel free
to replace it with any DRAWER type .info file.
8. Issue the CLI command "Run NETPAR-SERVER" on Machine A. This starts up
the server process (You can kill the server by BREAKing the CLI number
that it ran under).
9. Issue the CLI command "Mount NET:" on Machine B. The first reference
to NET: after the mount will load the handler.
You should now be able to cd into NET:, and a directory, Foo should
exist. Getting a directory of Foo (or any other operation) will
actually exercise the network so this is a good test. If it freezes
your cable is probably incorrectly wired
NOTE! Apparently MODEM cables can interfere with the parallel port
network. If it doesn't work, be sure there is nothing connected
to your serial port. The problem is that the RI (Ring Indicate) line
on the serial port interferes with the SEL line on the parallel port.
If you do have problems, you may have to cut the RI line (i.e. fool
around with your serial cabling).
============================================================================
Once the NET: device is running, you can use the provided NETMOUNT command
to allow access to other devices besides ROOT: on the remote machine.
NETMOUNT is a temporary stopgap until a real ROOT: device is implemented
that allows access to all devices on a machine via a single handler.
For now, the NETMOUNT command format is
NETMOUNT <local device> <node name> <remote device>
where <local device> is the name you MOUNTed (usually NET:)
<node name> is the name you want to refer to the new entry as
<remote device> is the name of the device on the remote node to use
For example,
NETMOUNT NET: DF0 DF0:
would allow you to access the floppy on the remote node by using the path
NET:DF0. Thus,
DIR NET:DF0
would produce the same results as doing a DIR DF0: on the remote machine.
============================================================================
REBOOTING
If you reboot one machine you MUST currently reboot the other as well.
===========================================================================
BOOT-STRAPPING NET:
(Advanced Users)
To Automate the process you want to 'RUN NETPAR-SERVER' on Machine A
in Machine A's startup-sequence.
You then want to setup Machine B's boot floppy with the minimal programs
required and a startup sequence which does nothing more than get NET:
up and running and then finishes booting of Machine A's HD.
Machine B's startup-sequence would look like this (This is the one
I use. P.S. my ENV: is in my SYS: directory):
----DF0:s/Startup-Sequence--------
setpatch
mount net:
net:foo/c/cd net:foo/c
resident resident
resident echo
resident execute
resident run
resident assign
resident path
Echo "Boot in Progress"
assign c: /c
assign t: ram:
assign s: /s
assign fonts: /fonts
assign sys: /
assign devs: /devs
assign libs: /libs
assign l: /l
assign sc: sys:sc
assign env: sys:env
path RESET c: sys:altc
resident CLI l:Shell-Seg SYSTEM ADD
mount newcon:
newshell newcon:30/40/610/160/AmigaDOS FROM s:standalone-startup
endcli >nil: <nil:
----------------------------------
Machine B's boot floppy must have the following files to work with the
example startup-sequence above.
ADDITIONALLY, THE HD ON MACHINE A MUST HAVE A COMPLETE WORKBENCH
DISTRIBUTION. The above sequence assumes all the standard
Assign'd names are in SYS:
DF0:L/Port-Handler
Disk-Validator
ConHandler
NewCon-Handler
Shell-Seg
NetPar-Handler (in this distribution)
Ram-Handler
DF0:S/Startup-Sequence (the file shown above)
DF0:Devs/Mountlist (contains entries for NET: and NEWCON:)
System-Configuration
DF0:Libs/icon.library
info.library
version.library
DF0:C/Run
Mount
SetPatch
Resident
*** You probably want to put more programs in
here like Type, and Editor, etc...
-------------------------------
Note that my startup-sequence references s:Standalone-startup. This file
is on Machine A's S: and contains further initialization. For example:
; Mount remaining Volumes (DHB-DH3 for my system)
netmount net: DHB DHB:
netmount net: DH0 DH0:
netmount net: DH1 DH1:
netmount net: DH2 DH2:
netmount net: DH3 DH3:
; Assign all your favoriate places
; (These are just examples)
assign alpha: net:DH0
assign beta: net:DH1
assign gamma: net:DH2
assign delta: net:DH3
Echo "Continuing..."
assign dist: Delta:dist
assign ltmp: Delta:ltmp
assign atmp: Delta:atmp
assign tmp: Delta:tmp
assign quad: ram:
assign dl: Delta:downloads
assign lib: alpha:lattice/lib
assign lc: alpha:lattice/c
assign include: alpha:lattice/include
assign lattice_include: alpha:lattice/CompactH
assign aztec_include: alpha:aztec/include
assign lattice: alpha:lattice
assign aztec: alpha:aztec
assign ol: gamma:openlook
assign autoincs: gamma:autoincs
assign autodocs: gamma:autodocs
assign private_include: alpha:include
assign text: gamma:text
assign dnet: gamma:src/dnet
assign games: alpha:games
assign fsrc: gamma:fsrc
assign src: gamma:src
assign srcc: gamma:c
assign sa: gamma:sa
assign altc: alpha:altc
; My Aztec C enviroment
Set CCTEMP=ram:
Set INCLUDE=aztec:include/!aztec:asm/
Set CLIB=aztec:lib/
; My standard shell-startup has all my NewShell
; aliases.
execute s:shell-startup